Note

Low Risk
Localized provider probe error typing and classification; behavior for callers using isCommandMissingCause is tightened but still covers platform NotFound and the new tagged error.

Overview
Replaces the message-only ProviderCommandExecutionError with a schema-backed ProviderCommandNotFoundError when a provider CLI is missing (e.g. Windows exit 9009). The error carries binaryPath, exitCode, and stdout/stderr lengths only—no subprocess text on the failure object, so diagnostics stay safe for logs/UI.

spawnAndCollect now fails with this type instead of a generic spawn … ENOENT string. isCommandMissingCause recognizes the tagged error and PlatformError NotFound spawn failures, and no longer treats arbitrary message substrings (e.g. legacy ENOENT strings) as missing-command signals.

New tests cover classification and that sensitive stderr is not exposed on the error or its message.

^{Reviewed by Cursor Bugbot for commit 507eee5. Bugbot is set up for automated code reviews on this repo. Configure here.}

Note

Structure provider command-not-found failures into a typed ProviderCommandNotFoundError

• Introduces ProviderCommandNotFoundError in providerSnapshot.ts, a schema-tagged error with binaryPath, exitCode, stdoutLength, and stderrLength fields and a stable message getter.
• Updates isCommandMissingCause to classify errors by normalized platform error type (PlatformError with reason NotFound) instead of parsing message strings; generic Error instances containing ENOENT no longer match.
• Updates spawnAndCollect to emit ProviderCommandNotFoundError (with structured diagnostics) instead of a message-only ProviderCommandExecutionError on Windows command-not-found exits.
• Adds tests in providerSnapshot.test.ts verifying classification behavior and that sensitive output (e.g. tokens in stderr) is not leaked in the error message.

^{Macroscope summarized 507eee5.}